chore: update pre-commit hook sp-repo-review #836
Conversation
eb1c950 to
52b797b
Compare
|
I am not sure how to test the changes for the |
|
we definitely do not want to merge any changes to our publishing workflow without tests in place. For example, a workflow that pushes to testpypi. I do not have access to testpypi for the zarr-developers organization -- it was claimed by @jakirkham, and he does not respond to any communication attempts. I opened a ticket to deal but so far no response from the pypi admins. Short-term we should probably make a |
|
Have followed up here: zarr-developers/zarr-python#3798 (comment) Let's continue discussion in that issue |
52b797b to
7c53c28
Compare
|
Rebased and temporarily ignoring GH105. The CI errors seem unrelated. |
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## main #836 +/- ##
=========================================
Coverage 100.00% 100.00%
=========================================
Files 27 27
Lines 901 901
=========================================
Hits 901 901 🚀 New features to boost your workflow:
|
7c53c28 to
f460d41
Compare
updates: - github.com/scientific-python/cookie: 2025.05.02 → 2026.04.04 enables a couple ingonred rules: - PY005: Has tests folder - PY006: Has pre-commit config - RF103: pyupgrade must be selected
PyProject:
└── PP304 Sets the log level in pytest ❌
log_level should be set. This will allow logs to be displayed on failures.
GitHub Actions: └── GH105 Use Trusted Publishing instead of token-based publishing on PyPI ❌
f460d41 to
c2e315a
Compare
updates:
https://learn.scientific-python.org/development/guides/gha-wheels/#publishing
TODO: